Search Results
Didn't find what you need in BMC Helix Discovery?
Search all docs.bmc.com documentation
Once you have created a model using start anywhere modeling (SAM), its state changes over time. Some changes are as a result of user … models are always published, once created, they have no other state. Managing models Effect of publishing a model A model only becomes
https://docs.bmc.com/docs/discovery/daas/lifecycle-of-a-start-anywhere-model-1207723290.html
anywhere modeling Lifecycle of a start anywhere model Service modeling with blueprints Services and application modeling home page … Suggested, _productNameLibraryno longer updates it during scanning. See Lifecycle of a model for more details. Published—Blueprint or start
https://docs.bmc.com/docs/discovery/daas/managing-models-993706261.html
contained in this document will help you understand the _productNameLibrary node lifecycle. This document details the internal components of BMC Discovery, the data model (for example, how virtualization hosts are modeled), and how to extend the data model. It is a good
https://docs.bmc.com/docs/discovery/daas/node-lifecycle-838555766.html
There were no model changes in _productNameLibrary 24.2 No new inferred nodes were added. No new DDD nodes were added. model_changes model Published by Scroll Versions from space DISCOMASTER and version 24.2
https://docs.bmc.com/docs/discovery/daas/model-changes-1007077639.html
Modeling tools Managing models Lifecycle of a start anywhere model For example, the _productNameLibrary demonstration contains … it as changes in the environment are discovered, as described in Lifecycle of a start anywhere model. Editing the model definition
https://docs.bmc.com/docs/discovery/daas/creating-a-start-anywhere-model-1207723267.html
to the application model. For more information about how models are updated, see Lifecycle of a start anywhere model. Static models You … services. Start anywhere modeling (SAM) enables you to create a model by choosing a starting point, visualizing it, and selecting from
https://docs.bmc.com/docs/discovery/daas/start-anywhere-modeling-1207723266.html
The default data model diagrams show the _productNameLibrary default shipping model including the main sections of the model. The diagrams should be useful if you are building searches and using the model to understand it. The aim of the diagrams are to be a quick
https://docs.bmc.com/docs/discovery/daas/the-default-data-model-838555769.html
, or instances of a multi-instance model Lifecycle-related attributes node_id automatic The hex node id of the ModelDefinition node used … A Model Definition is described by a JSON object with the following keys: JSON format for conditions rules and queries JSON format
https://docs.bmc.com/docs/discovery/daas/json-format-keys-for-model-definitions-1104116602.html
This section provides a reference on the tools available in the visualizations and application editing view. Managing models Creating a start anywhere model Lifecycle of a start anywhere model Software and infrastructure visualization help_model_applications
https://docs.bmc.com/docs/discovery/daas/modeling-tools-993706260.html
it comes into existence, and the conditions under which it ceases to exist. For nodes in the _productNameLibrary model, the lifecycle stages are: Current - The lifecycle stage used to describe nodes which exist in your model. _productNameLibrary has evidence
https://docs.bmc.com/docs/discovery/daas/key-terminology-838555783.html
opens. In the Model section, click Custom Categories. Accessing data in the standard categories The Custom Categories page shows tabs … product families. Lifecycle Status Status values that can be associated with the IT components managed in your organization. See
https://docs.bmc.com/docs/discovery/daas/setting-up-standard-data-categories-838555758.html
You can model your services by using blueprints. _productNameLibrary provides default blueprints, and you can use those to create your own services. You can also create blueprints from scratch. Service modeling with blueprints Managing models Regular expressions
https://docs.bmc.com/docs/discovery/daas/modeling-services-by-using-blueprints-1207723245.html
Service and application modeling helps make it quicker and easier to create a focused model, and it enables you to choose any entry points into a Business Service, Business Application, or Technical Service and begin modeling from there. It gives you the choice
https://docs.bmc.com/docs/discovery/daas/service-and-application-modeling-993706240.html
The _productNameLibrary data model and the approach to data storage enables you to model complex IT environments in such a way that the model is a very close representation of the actual environment. This document describes the mapping between the model and the real
https://docs.bmc.com/docs/discovery/daas/model-summary-838555767.html
Model node existence functions The model scope is automatically populated with a function named after each node kind defined … on the node: my_host := // a Host from somewhere my_host.color := "red"; // Good! Model relationship existence functions Where additional
https://docs.bmc.com/docs/discovery/daas/model-functions-838555976.html
as a: working back-up during modelling application modelling backup in case of required appliance maintenance (for example, a model reinitialization) You can also export application model definitions and move them to another system. The same application model definitions can
https://docs.bmc.com/docs/discovery/daas/exporting-and-importing-application-model-definitions-838557062.html
needs. Blueprints are templates that give you complete control of the service that you are modeling. You can use both static and dynamic content to control the model composition. Service and application modeling Managing models Blueprints Blueprints are predefined
https://docs.bmc.com/docs/discovery/daas/service-modeling-with-blueprints-1207723231.html
Making a change to an application mapping definition (the CAM model) increases the major version of the generated The Pattern Language (TPL). A major version change means that a new model is built in the datastore with the new patterns maintaining it. However, the old
https://docs.bmc.com/docs/discovery/daas/saving-or-editing-the-cam-model-838557068.html
Content in a Start Anywhere Model (SAM) or a static model is described using a JSON structure. JSON format for conditions rules and queries JSON format keys for model definitions The JSON structure has the following objects: Key Required? Description nodes Yes Object
https://docs.bmc.com/docs/discovery/daas/json-format-for-model-contents-1104116601.html
You can modify settings for maintaining your data model, including aging limits, in the Model Maintenance settings of the user interface. To configure model maintenance settings: From the main menu, click the Administration icon. The Administration page opens
https://docs.bmc.com/docs/discovery/daas/configuring-model-maintenance-settings-838555752.html
modeling became available in the Technology Knowledge Update 2014-Aug-1.) To create a static application model From the top menu, open Model > Services & Applications. Click Create/Import. Click the Create Legacy CAM tab. In the Create group for mapping field, create
https://docs.bmc.com/docs/discovery/daas/creating-a-static-application-model-838557070.html
during discovery and build the appropriate model whenever your application is discovered. BMC Discovery can discover and automatically build … for download. In Service and application modeling however, you can create SIs from discovered processes or services. To generate
https://docs.bmc.com/docs/discovery/daas/generating-patterns-for-the-application-model-838557053.html
A Host Container node is used to model a system that is logically partitioned into a number of hosts, but is not a directly discoverable host itself. Systems that contain a number of physically separate devices, such as blade enclosures, are modeled as a Hardware
https://docs.bmc.com/docs/discovery/daas/host-container-node-838555810.html
and there is no parent), they are consolidated into clusters which are modeled as Cluster nodes, see Cluster node lifecycle. For example … infrastructure. Host node lifecycle The following section describes the scenarios in which a Host node is created, updated or destroyed
https://docs.bmc.com/docs/discovery/daas/host-node-838555811.html
, the Host Container node is used. Hardware Container Lifecycle Hardware containers are created and maintained by patterns. The details … in which a Hardware Container is created, updated or removed. Creation When a chassis management controller is discovered, this is modeled
https://docs.bmc.com/docs/discovery/daas/hardware-container-node-838555809.html